Until recently, I mainly used the opening_hours evaluation tool to quickly generate valid OSM opening hours. However, it often requires some manual work to simplify the syntax afterwards.

That’s why I tried using ChatGPT instead - and it works surprisingly well. You can simply copy and paste opening hours from websites, or even upload an image, and ask it to format them for the opening_hours tag.

Example

LLM query

please format the opening hours in the attached image for the OSM 'opening_hours' tag.

Output

Mo 13:00-18:00; Tu-Th 09:30-18:00; Fr 09:30-21:00; Sa 09:00-17:00; Su off

This is a rather simple example, but it also works well with more complex opening hours.

Taking info from

https://www.rigacci.org/wiki/doku.php/doc/appunti/hardware/gps_logger_i_blue_747

and

https://www.technologyblog.de/2019/05/gps-rollover-zerstoert-gps-logger/

and

https://wiki.openstreetmap.org/wiki/Holux_M-241

a modified mtkbabel can set the time when reading from the device. That should probably go into some check whether it’s really a M-241 that is connected, but as long as the battery lasts the device shows the correct time again and logs tracks in this year and not dated 2006..

$ diff -u /usr/bin/mtkbabel ./mtkbabel
--- /usr/bin/mtkbabel   2019-10-12 12:23:29.000000000 +0200
+++ ./mtkbabel  2026-03-03 19:37:37.482923895 +0100
@@ -166,7 +166,7 @@
 #-------------------------------------------------------------------------
 my $debug    = $LOG_WARNING;     # Default loggin level.
 my $port     = '/dev/ttyUSB0';   # Default communication port.
-my $baudrate = 115200;           # Default port speed.
+my $baudrate = 38400;           # Default port speed.
 my $ro_weeks = 0;                # Weeks offset to fix Weeks Rollover Bug

 # GPX global values.
@@ -356,6 +356,18 @@
     set_data_types($model_id);
 }

+# Set time to work around week rollover bug
+
+my ($sec,$min,$hour,$mday,$mon,$year) = gmtime;
+
+$year += 1900;      # year is years since 1900
+$mon  += 1;         # month is 0-11
+
+packet_send(sprintf('PMTK335,%04d,%02d,%02d,%02d,%02d,%02d', $year, $mon, $mday, $hour, $min, $sec));
+$ret = packet_wait('PMTK001');
+printf "Set time string: $year, $mon, $mday, $hour, $min, $sec\n";
+printf "Return for setting time: $ret\n";
+
 #-------------------------------------------------------------------------
 # Erase memory.
 #------------------------------------------------------------------------- 

I have created a tag, diet:excipient_free=* , which is about finding clean supplements, i.e., without harmful ingredients that can make us infertile, inflamed, obese or even epileptic.

For example, whenever we look for magnesium (bis)glycinate, we want one thing, but many so-called “magnesium” supplements come with a lot more ingredients that might reduce the price, or enhance the appearance, but of course, at a cost; to hurt and make us need another supplement to compensate with the side effects. (Maybe they should rename those “magnesium” supplements to corn syrup supplements instead.)

Almost if not all of those ingredients fall into one category, excipients. Let’s use diet:excipient_free=* on pharmacies and nutrition supplement stores to promote a healthier future without dyes, fillers, flavorants, preservatives and other inactive ingredients that can cost us our health.

🌳 Percebendo que havia poucas informações no OpenStreetMap sobre o Parque Evaldo Cruz, em Campina Grande - PB, iniciei há uns meses o micromapeamento da área motivado pela reforma que ocorreu no local, por ser uma área verde que frequento cotidianamente e ser parte do Parque do Povo, onde acontece o Maior São João do Mundo.

Identificação em campo de Handroanthus impetiginosus (Ipê-roxo-de-bola)

📚 Sou pesquisador da área ambiental então sempre tento mostrar o potencial que o mapeamento para o OpenStreetMap possui. Os resultados abaixo são relacionados às árvores mapeadas e identificadas no local do parque, um trabalho que iniciei faz mais de seis meses e está quase 100% pronto. Quem quiser acompanhar esses e outros mapeamentos, costumo divulgá-los no Instagram - OMapaPB.

… See full entry

Gente que fecha nota dizendo que resolveu o problema, mas não resolve. Ou gente que resolve mas não fecha a nota.

OpenStreetMap old timers know about the infamous 2009 TIGER import of road data in the US that continues giving to this day. Our story has none of the, maybe deliberate, shenanigans (see the TIGER improvement project) that went on back then in the US, but there are clearly some similarities in the lessons that should be learnt.

Back in July of 2011 the Swiss community undertook a big effort to import municipality boundaries from swisstopo (the marketing name of the federal Swiss GIS department) (see osm.wiki/Switzerland/swissBOUNDARIES3D). Being an OSM n00b at the time with just a bit over a year editing experience I didn’t really do anything useful for the import proper, but I did organise the explicit permission needed from swisstopo as this was many years before their data would become available for use on open terms for us in September 2021. With a couple of technical hiccups along the way that are not really documented, we finally managed to complete the work by early August.

Fast forward to today: I’ve been going on for a few years now that we really need a quality assurance process so that we can discover and track differences between swisstopos data and what is in OSM. We knew and fully expected that there would be differences, because:

• at the time of the import we simplified the boundaries quite significantly because of the resource constraints of the computer hardware available to us,
• over the last 14 years we independently followed the mergers and other changes of the municipalities (see osm.wiki/Switzerland/2026_Municipality_Mergers), and on the one hand didn’t expect this to improve the accuracy of the boundaries, and we knew that very rarely their would be associated minor geometry changes that we wouldn’t be able to track,
• and then just general decay due to glueing and accidental modifications.

… See full entry

Привет сообществу OpenStreetMap!

Не знаю, будет кто-то читать эту запись или нет, но попробовать написать в дневник — очень интересный опыт. Нигде не слышал, что здесь есть такой функционал, а раз имеется 😊 — нужно пользоваться.

В этой записи я хотел бы поделиться своим первым опытом. По сути, этот текст будет «водой» и не принесет много полезной информации.

Как я стал мапером

Однажды мне потребовалось найти адрес в моем поселке, но каково же было мое удивление, когда выяснилось, что никаких адресов нет (по крайней мере, точных). Мало того, отсутствовали и ключевые объекты инфраструктуры.

Недолго думая, я начал искать информацию о том, как редактируют карты, и наткнулся на «Народную карту» Яндекса. Какое-то время я вносил правки там: добавил и исправил достаточно много объектов. Процесс показался, как ни странно, очень интересным и «залипательным» — так у меня появилось хобби в картографии.

Знакомство с OSM

О проекте OSM я знаю относительно давно, но особого внимания ему не уделял. Как я сейчас понимаю — очень зря! Такого классного редактора, как iD, я еще не видел. Инструменты настолько простые, что ты не работаешь ими, а получаешь наслаждение, если так можно выразиться.

Про документацию я вообще молчу! Она бесподобна. Снимаю шляпу перед людьми, которые переводили её на русский язык. С ней очень удобно работать: один клик — и ты уже читаешь именно то, что тебе надо, а не тонну неструктурированной и разбросанной информации.

Итоги

Как проходит одобрение правок и когда они появятся на основной карте — я пока не знаю, да на данном этапе это и не важно. Надеюсь, что быстро.

В общем, очень жалею, что раньше не редактировал здесь и не уделял проекту внимания. Проект классный, документация — моё почтение, инструменты на высоте!

Всем спасибо за внимание, всем пока!

Прогулка с StreetComplete — добавил 300+ объектов в Минске. Приятно видеть, как карта наполняется деталями!😊

3 March 2026: Writing this at a Missing Maps “London” remote meeting, realizing that I’d never written a OSM diary about the research I did within the ecosystem. I’m so late! But I’d love to still write this down.

I started a new wiki talk page discussion on the conflicting/controversial usage of the wetland=tidalflat tag regarding implied and explicit surface types:

• Change of definition to mainly encompass mud and discourage use on sand flats

Also posted a comment on positive related changes being worked on by the carto team:

• openstreetmap-carto PR: #5067 Use dedicated style for landcover polygons over water

Hoy comienzo la plenitud de mi sinceridad

Every map tells a story. Some stories are drawn with roads and buildings. Others are written through people, voices, and lived experiences. This is the story of how mapping became a bridge between climate vulnerability and community resilience in the heart of Dhaka. Under the Climate Resilience Fellowship, proudly supported by OpenMappingHub Asia Pacific, our Team 8 embarked on a journey called “Healthy Homes, Safer Futures.” Our goal was simple yet powerful: to strengthen climate awareness and resilience among vulnerable communities living in Dhaka’s urban informal settlements.

Where It All Began

In early May, all ten fellowship teams gathered in Dhaka, sharing ideas and aspirations for climate action. We were two coordinators: Mohammad Azharul Islam — Oceanographer and GIS Analyst at the Center for Geoservice and Research Ahsan Habib Saimon — Capacity Building Officer at Christian Commission for Development in Bangladesh Together, they envisioned a project that would connect data, digital tools, and grassroots knowledge to create safer living environments.

… See full entry

Nimman Road, Chiang Mai(Thailand) is a well-mapped, high-traffic corridor. It scores a B on network density: good intersection frequency, reasonable block lengths. But it scores near zero on crossing coverage because there are no highway=crossing nodes tagged within the 800m analysis radius. The street has physical crossings. They’re just invisible to any tool that relies on OSM, which is most tools.

That’s what SafeStreets shows: not just a score, but which data gap is causing it.

What SafeStreets is?

A free tool that scores the walkability and pedestrian safety of any street address globally(graded out of 10). No account required, 190+ countries. OSM is the backbone, and the only data source that works everywhere.

How OSM powers it, three functions?

… See full entry

Portal North Bridge construction and study documents

https://archive.org/details/@isstatenisland/lists/7/portal-bridge-documents?sort=date

I gathered and uploaded documents relating to the Portal Bridge capacity enhancement project and its replacement, Portal North Bridge. The documents (except the Amtrak bulletins) come from NJDEP’s DocMiner. The Amtrak bulletins were retrieved by FOIA request. It appears the FEIS disappeared off the web many years ago.

The original plans intended to build a 3-track fixed span to the north. The documents from 2019 and later depict the currently chosen plan, the two-track fixed structure to the north. The south structure is not funded.

https://archive.org/details/portal-bridge-project-feis-final-4f-october-2008 Portal Bridge Capacity Enhancement Project - Final Environmental Impact Statement and Final Section 4(f) Evaluation, October 2008

https://archive.org/details/portal-bridge-project-feis-final-4f-appendix-vol1-october-2008 Portal Bridge Capacity Enhancement Project - Final Environmental Impact Statement and Final Section 4(f) Evaluation, October 2008: Appendix Volume 1

https://archive.org/details/portal-bridge-project-feis-final-4f-appendix-vol2-october-2008 Portal Bridge Capacity Enhancement Project - Final Environmental Impact Statement and Final Section 4(f) Evaluation, October 2008: Appendix Volume 2

https://archive.org/details/portal-bridge-project-relocation-study-january-2010 Portal Bridge Capacity Enhancement Project - Relocation Feasibility Study, January 2010

https://archive.org/details/portal-bridge-project-gc02-construction-plan-sheets-2019 Portal Bridge Capacity Enhancement GC.02 Contract - Construction Plan Sheets, August 15th 2019

https://archive.org/details/portal-bridge-project-environmental-impact-sheets-2020-2025 Portal Bridge Capacity Enhancement Project - Environmental Impact Sheets, January 2020 with November 2025 modifications

… See full entry

Всем привет! Я GISTracer из Минска.

По базовому образованию — технолог-машиностроение. Работа с чертежами, допусками и технической документацией выработала главные качества: внимательность, усидчивость и привычку к точности. Именно они привели меня в OpenStreetMap.

Сейчас вхожу в тему профессиональной картографии и ГИС. Интересуюсь качественной векторизацией по спутниковым снимкам, работой в JOSM и постепенно наполняю карту полезными деталями.

Понимаю, что хорошая карта — это тысячи мелких правок, сделанных с вниманием. Этим и планирую заниматься.

Буду рад обратной связи и советам от опытных участников. Всем качественных тегов и чистых подложек!

1. 你驾车，Android Auto上使用OSM导航软件
2. 副驾不能晕车，放个笔记本在大腿上，在iD上连接两点，用编辑器把缺失的路现画上
3. 你在导航上规划路线，看哪里特别绕
4. 副驾对着卫星图画缺少的路
5. 你开车，副驾补全车道和路线信息

Manchmal sind es die kleinen Details. Dank 360° Mapillary Bildern konnte ich an der Stelle die Gegend etwas “aufhübschen”. Auch wenn man natürlich nicht für den Renderer mappen soll. Aber ein paar Dinge sind doch nützlicherweise hinzugekommen.

… See full entry

谁有中国地区电网数据

Como corrigir o nome de uma rua na aplicação CNEFE

Corrigir um nome de rua usando a aplicação CNEFE – Logradouro é um processo simples e direto, integrando os dados oficiais do Instituto Brasileiro de Geografia e Estatística com o mapa colaborativo do OpenStreetMap.

Veja o passo a passo:

1️⃣ Escolha a área no mapa Acesse a aplicação e navegue pelo mapa até a cidade ou bairro desejado. Você pode usar o zoom e arrastar o mapa para localizar a região onde deseja verificar os nomes das ruas.

2️⃣ Use o filtro “Rua” No painel de filtros, selecione a opção Rua. Isso fará com que a aplicação mostre apenas os logradouros classificados como ruas, facilitando a identificação de divergências entre o CNEFE e o OSM.

3️⃣ Escolha o editor A aplicação permite abrir a edição diretamente em um editor do OSM. Você pode escolher, por exemplo:

Editor iD (no navegador) JOSM (editor avançado para desktop)

Selecione o editor com o qual você já trabalha.

… See full entry

‘De Wasvrouwen’ is een beeld van Carla Rump in Groet, Noord-Holland.
Link naar de locatie met tags op OSM.
Het beeld is een creatie van Carla Rump.